✅ Deploy Preview for pauseai ready!

Name	Link
🔨 Latest commit	26a31f1
🔍 Latest deploy log	https://app.netlify.com/projects/pauseai/deploys/68bd01287f04a400089133eb
😎 Deploy Preview	https://deploy-preview-447--pauseai.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 40 (🔴 down 18 from production) Accessibility: 89 (no change from production) Best Practices: 100 (no change from production) SEO: 90 (🔴 down 9 from production) PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Environment Variable Fix Applied

Just merged a fix from main that addresses the TRANSLATION_OPENROUTER_API_KEY vs L10N_OPENROUTER_API_KEY inconsistency we discovered.

The Issue

• scripts/inlang-settings.ts was checking for TRANSLATION_OPENROUTER_API_KEY (old name)
• All other l10n scripts use L10N_OPENROUTER_API_KEY (new name)
• This mismatch could cause builds to unexpectedly run in dry-run mode

The Fix (commit fd6eac2)

• Changed inlang-settings.ts to use L10N_OPENROUTER_API_KEY consistently
• Added a dev-machine-only warning for the deprecated name
• Production remains safe because:
  • Netlify currently has both env vars set
  • Production only builds English (always dry-run mode)
  • CI environments skip the deprecation check

Next Steps

After this deploys successfully, we can remove TRANSLATION_OPENROUTER_API_KEY from Netlify configuration.

The latest build should now use the correct env var consistently.

borja left a comment:

Hi Anthony, Borja Here. I have a few comments from the Spain group

Path:      /es/proposal
Browser:   Mobile Safari 18.6 on iOS 18.6.2
Viewport:  430 x 746 @3x
Language:  es-ES
Cookies:   Disabled

Open Deploy Preview · Mark as Resolved

Hi team,

Recently i joined the spanish working group and said i would try to be on top of this. Our current standpoint is quality is good enough for this to reach production and we assume we can keep iterating on top of it. Spanish communities in our view tend not to have a fair english level so we believe releasing this version of the spanish translations would help a great deal.

Thanks in advance!

The issues we could spot doing a review are

• Translation improvement for /es/riesgos #503
• Translation improvement for /es/posts #504
• Translation improvement for /es/communities #505
• Translation improvement for /es/join #506
• Translation improvement for /es/statement #507
• Translation improvement for /es/pdoom #508
• Translation improvement for /es/quotes #509
• Translation improvement for /es/email-builder #510
• Translation improvement for /es/outcomes #511

Thanks. I thought I'd set things up to tell me when these issues were opened but apparently not. Until I fix that by all means @anthonybailey or assign me.

The general case of "this special page lacks translations" basically maps to the page not by being a slugged "post", but rather through special case +page.ts and +server.ts wrappers. Thanks for calling out particular prominent ones.

The website homepage is one special case but some effort has been made there - spot any problems there?

Dynamic pages are harder to l10n than static ones in the current system. I will look out for general patterns to help while working on individual cases.

The website homepage is one special case but some effort has been made there - spot any problems there?

Nope, homepage looks spot on

Ok, so all problems reported are either "this special page is still English" or "l10ns broke my link". Serious problems, of course.

Any specific places where you would go "this word is a bad choice" or "in general, the tone is wrong" or "see, in Spain, I'd have expected a different kind of 'you' when the site addresses the reader" etc?

Ok, so all problems reported are either "this special page is still English" or "l10ns broke my link". Serious problems, of course.

yup, pretty much these issues

Any specific places where you would go "this word is a bad choice" or "in general, the tone is wrong" or "see, in Spain, I'd have expected a different kind of 'you' when the site addresses the reader" etc?

We had someone review the site and no "wrong choice of word or tone" was spotted. There is a comment regarding inconsistent "kind of you" but not a particular example was given and I cannot spot it myself. To my eyes the content is using (at least mostly) the right "kind of you".

That's reassuring. This is only using Llama currently so seems certain auto-translation can be as great as we need.

Once I've got collage work PauseAI/pauseai-collagen#1 out the way I'll move back to this.

Joining dots...

This remains in draft. So you should see changes in the Git repos but only on the branch best I know.

We are looking to fix issues and productionize in some way.

We are happy to publish current l10n to es to those readers, once links are fixed and special case pages remaining in English are acknowledged to be in that state when es readers see them.

There are two directions here with with overlap.

Doing it on the main website with suitable workarounds for lack of prefix-all-locales redirection and associated 500 responses is best.

As an intermediate informing the same work serving static copies of fixed pages from PauseAI.es is planned. @danilupion has most focus on this. #515 is part of that work but I understand it went slightly awry.